domainDelete Message Type
Further content in this topic
K/V Keyword | XML Namespace and Element | Occurrence min - max | Type / Length | Value Range | Description |
---|---|---|---|---|---|
Result | result | 1 | enumeration | result-erule | Result of processing success = order was carried out failed = order was not carried out exception = system malfunction, request was not carried out |
StId | stid | 1 |
token 30-255 |
stid-rule | A server transaction ID (StId) assigned by the server. The StId is used to globally and unambiguously reference the provider's request and the corresponding response from DENIC. |
MsgCnt | msgcnt | 1 |
token 1 - 7 |
digit-rule |
Without “MsgType”, the total number of messages is displayed; with “MsgType”, the number of messages for the specific type is displayed. For K/V format only: if this field contains the value 0, there are no messages in the entire message queue. For XML, msgcnt is only displayed if there is at least one message in the queue. |
MsgTime | msgtime | 1 |
dateTime 25 |
date-rule | The time of message creation |
MsgId | msgid | 1 |
token 30-255 |
msgid-rule | The message ID of the message |
MsgType | - | 1 | enumeration | msgtype-erule | The category of the message issued |
Domain | domain:handle | 1 | token 4 – 66 | domain-rule | Domain name |
Domain-Ace | domain:ace | 0-1 | token 4 - 66 | domainace-rule | Domain name in ACE form (ASCII Compatible Encoding). |
Message |
<msg:message level=“info“ code=“16350000031„> <tr:text>Domain has been deleted [request-reference DENIC#:[Ticketnummer]</tr:text></msg:message> |
1 |
normalizedString 1 - 255 |
message-rule | Message line with a fixed code, text and a variable ticket number Note: The ticket number is a reference to a process and must be provided to the DENIC legal department in the event of queries. |
Special features of the domainDelete message type
-
“domainDelete” is a message about a domain deletion carried out by DENIC.
-
Their could be different reasons in the information part of the message, why a domain was deleted. One of them could be reference to a ticket ID from DENIC's internal ticket management system.
-
In case of a ticket ID or no ticket ID/no reason our member support DENIC Business Services (DBS) can help with information.
-
-
In a K/V format example, the message lines would look like this:
-
Domain in “serverHold” status, the verification period has expired:
Copymessage: 16350000031 Domain has been deleted [no verification information provided]
-
Domain with a ticket ID:
Copymessage: 16350000031 Domain has been deleted [request-reference DENIC#:2024100143000000]
-
Domain without ticket ID and without reason for deletion:
Copymessage: 16350000031 Domain has been deleted []
Examples
- xml
- k/v
format: xml
request: domainDelete
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<registry-request xmlns="http://registry.denic.de/global/5.0" xmlns:msg="http://registry.denic.de/msg/5.0">
<msg:queue-read msgType="domainDelete"/>
</registry-request>
format: xml
response: domainDelete
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>ae029b0a-50af-11e0-b375-95a6041ce317</tr:stid>
<tr:result>success</tr:result>
<tr:data>
<msg:message xmlns:msg="http://registry.denic.de/msg/5.0" msgid="ee6bfa7f-4afd-11e0-ad4b-47ecb35e56d2" msgcnt="1" msgtime="2011-03-10T11:05:30+01:00">
<msg:domainDelete>
<msg:domain>
<msg:handle>de-domain.de</msg:handle>
<msg:ace>de-domain.de</msg:ace>
</msg:domain>
<msg:message level="info" code="16350000031">
<tr:text>Domain has been deleted</tr:text>
<tr:argument>request-reference DENIC#:2011031043000000</tr:argument>
</msg:message>
</msg:domainDelete>
</msg:message>
</tr:data>
</tr:transaction>
</registry-response>
format: xml
response: domainDelete
status: was serverHold
verification time up
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>ae029b0a-50af-11e0-b375-95a6041ce317</tr:stid>
<tr:result>success</tr:result>
<tr:data>
<msg:message xmlns:msg="http://registry.denic.de/msg/5.0" msgid="8960348c-6879-cb92-2b6f-cbc9abf98080" msgcnt="1" msgtime="2024-06-01T15:51:08+02:00">
<msg:domainDelete>
<msg:domain>
<msg:handle>de-example.de</msg:handle>
<msg:ace>de-example.de</msg:ace>
</msg:domain>
<msg:message level="info" code="16350000031">
<tr:text>Domain has been deleted</tr:text>
<tr:argument>no verification information provided</tr:argument>
</msg:message>
</msg:domainDelete>
</msg:message>
</tr:data>
</tr:transaction>
</registry-response>
format: xml
response: domainDelete
ticket: available
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>ae029b0a-50af-11e0-b375-95a6041ce317</tr:stid>
<tr:result>success</tr:result>
<tr:data>
<msg:message xmlns:msg="http://registry.denic.de/msg/5.0" msgid="8960348c-6879-cb92-2b6f-cbc9abf98080" msgcnt="1" msgtime="2024-06-01T15:51:08+02:00">
<msg:domainDelete>
<msg:domain>
<msg:handle>de-example.de</msg:handle>
<msg:ace>de-example.de</msg:ace>
</msg:domain>
<msg:message level="info" code="16350000031">
<tr:text>Domain has been deleted</tr:text>
<tr:argument>request-reference DENIC#:2024100143000000</tr:argument>
</msg:message>
</msg:domainDelete>
</msg:message>
</tr:data>
</tr:transaction>
</registry-response>
format: xml
request: domainDelete
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<registry-request xmlns="http://registry.denic.de/global/5.0" xmlns:msg="http://registry.denic.de/msg/5.0">
<msg:delete msgid="02699380-9c7a-11de-8188-9ff72af94906" msgType="domainDelete"/>
</registry-request>
format: xml
general response to all QUEUE-DELETE requests
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>078db1bf-9f0a-11df-a9e2-9519b5688882</tr:stid>
<tr:result>success</tr:result>
</tr:transaction>
</registry-response>
format: k/v
response: domainDelete
Result: success
STID: 78bf488c-9f0c-11df-a9e2-9519b5688882
Msgcnt: 1
Msgtime: 2011-03-10T11:05:30+01:00
Msgid: ee6bfa7f-4afd-11e0-ad4b-47ecb35e56d2
Msgtype: domainDelete
Domain: de-example.de
Domain-ace: de-example.de
Message: 16350000031 Domain has been deleted []
format: k/v
response: domainDelete
status: was serverHold
verification time up
Result: success
STID: 253526e9-9f04-11df-a9e2-9519b5688882
Msgcnt: 1
Msgtime: 2024-06-01T15:51:08+02:00
Msgid: 8960348c-6879-cb92-2b6f-cbc9abf98080
Msgtype: domainDelete
Domain: de-example.de
Domain-ace: de-example.de
Message: 16350000031 Domain has been deleted [no verification information provided]
format: k/v
response: domainDelete
ticket: available
Result: success
STID: 253526e9-9f04-11df-a9e2-9519b5688882
Msgcnt: 1
Msgtime: 2024-06-01T15:51:08+02:00
Msgid: 8960348c-6879-cb92-2b6f-cbc9abf98080
Msgtype: domainDelete
Domain: de-example.de
Domain-ace: de-example.de
Message: 16350000031 Domain has been deleted [request-reference DENIC#:2024100143000000]
format: k/v
request: domainDelete
Version: 5.0
Action: queue-delete
Msgid: b988dae0-ae64-11de-b15c-f1279ab97beb
Msgtype: domainDelete
CTID: bre-34634621634
format: k/v
general response to all QUEUE-DELETE requests
Result: success
STID: 0b97f9b7-9f0b-11df-a9e2-9519b5688882
CTID: bre-34634621634
format: e-mail
message type: domainDelete
environment: live
From: registry-response@denic.de
Subject: DOMAIN DELETE information - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET:
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted
format: e-mail
message type: domainDelete
environment: live
status: was serverHold
verification time up
From: registry-response@denic.de
To: <regacc-email>
Subject: DOMAIN DELETE information - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET:
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted [no verification information provided]
format: e-mail
message type: domainDelete
environment: live
ticket: available
From: registry-response@test.denic.de
To: <regacc-email>
Subject: DOMAIN DELETE information TEST - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET: DENIC#:2024100143000000
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted
format: e-mail
message type: domainDelete
environment: test
From: registry-response@test.denic.de
Subject: DOMAIN DELETE information TEST - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET:
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted
format: e-mail
message type: domainDelete
environment: test
status: was serverHold
verification time up
From: registry-response@test.denic.de
To: <regacc-email>
Subject: DOMAIN DELETE information TEST - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET:
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted [no verification information provided]
format: e-mail
message type: domainDelete
environment: test
ticket: available
From: registry-response@test.denic.de
To: <regacc-email>
Subject: DOMAIN DELETE information TEST - 2023-09-27T16:15:15+02:00
STATUS: success
TICKET: DENIC#:2024100143000000
OBJECT: Domain
HANDLE: dänic.de [xn--dnic-loa.de]
INFO: 16350000031 Domain has been deleted